Supported Metrics
The following tabs represent the Metric Category of Wireless Lan Controller.
For Cisco Table
| Native Type | Metric Name | Display Name | Units | Application Version | Description |
|---|---|---|---|---|---|
| Wireless LAN Controller (Cisco) | wlan_controller_ifOperationalStatus | WLC IfOperational Status | 2.0.0 | The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components. possible values are UP : 1,DOWN: 2,TESTING: 3,UNKNOWN: 4,DORMANT: 5 and NOTPRESENT: 6. | |
| wlan_controller_ifAdminStatus | WLC IfAdmin Status | 2.0.0 | The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state). possible values are UP : 1,DOWN: 2 and TESTING: 3. | ||
| Wireless LAN Controller Access Point | wlan_controller_ap_operationStatus | WLC AP Operation Status | 1.0.0 | Operation State of the AP. When AP associates with the Airespace Switch its state will be associated. When Airespace AP is disassociated from the Switch, its state will be< disassociating. The state is downloading when the AP is downloading its firmware. possible values are associated(1), disassociating(2), downloading(3). | |
| wlan_controller_ap_adminStatus | WLC AP Admin Status | 1.0.0 | Admin state fo the AP. Possible values are enable(1), disable(2). | ||
| wlan_controller_ap_coverageProfilestate | WLC AP Coverage Profile State | 1.0.0 | This field represents the current state of coverage monitor. This is a total measurement of the client coverage at this Airespace AP. Possible values are 0- Fail : Indicates the Airspace AP is not performing adequately against the coverage profile, 1- PASS indicates that this Airespace AP is performing adequately compared to the coverage profile. | ||
| wlan_controller_ap_noiseProfilestate | WLC AP Noise Profile State | 1.0.0 | This field represents the current state of Noise monitor. This is a total measurement of the noise present at this Airespace AP. Possible values are 0- Fail : Indicates the Airespace AP is not performing adequately against the noise profile, 1- Pass: Indicates that this Airespace AP is performing adequately compared to the noise profile. | ||
| wlan_controller_ap_interferenceProfileState | WLC AP Interference Profile State | 1.0.0 | Monitors the current state of Interference monitor. This is a total measurement of the interference present at this Airespace AP. Possible values are 0- Fail : Indicates the Airespace AP is not performing adequately against the Interference profile. 1- Pass : Indicates that this Airespace AP is performing adequately compared to the Interference profile. | ||
| wlan_controller_ap_loadProfileState | WLC AP Load Profile State | 1.0.0 | Monitors the current state of the load monitor. This is a total measurement of the business of this Airespace AP. Possible values are 0- Fail : Indicates the Airespace AP is not performing adequately against the LOAD profile, 1- Pass: indicates that this Airespace AP is performing adequately compared to the Airespace AP profile. |
For Aruba Model
| Native Type | Metric Name | Display Name | Units | Application Version | Description |
|---|---|---|---|---|---|
| Wireless LAN Controller Access Point | aruba_wlan_controller_CardStatus | Aruba Controller Card Status | 3.0.0 | Provides Aruba controller card type and the status. Possible card types are 1- LC1,2- LC2,3- SC1,4- SC2,5- SW2400,6- SW800,7- SW200,8- M3MK1,9- SW3200,10- SW3400,11- SW3600. Possible card status values are 1- Active,2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.16.1.2,1.3.6.1.4.1.14823.2.2.1.2.1.16.1.12]. | |
| aruba_wlan_controller_SwitchStatus | Aruba Controller Switch Status | 3.0.0 | Provides Aruba controller switch status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.6, 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.2, 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.5]. | ||
| aruba_wlan_controller_FanStatus | Aruba Controller Fan Status | 3.0.0 | Provides Aruba controller fan status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2]. | ||
| aruba_wlan_controller_PowerSupplyStatus | Aruba Controller Power Supply Status | 3.0.0 | Provides Aruba controller powersupply status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.18.1.2]. | ||
| aruba_wlan_controller_ap_status | Aruba WLAN AP Status | 3.0.0 | Monitors the Aruba WLAN AP Status. [WLSX-WLAN-MIB :: wlanAPStatus : 1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.19]. Possible Values are 1: up, 2: down. | ||
| Wireless LAN Controller InstantOn Access Point | aruba_wlan_controller_instanton_ap_Status | Aruba AP Status | 3.0.0 | Monitors the Access Point status. [OIDs: 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.2, 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.1, 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.11]. | |
| aruba_wlan_controller_instanton_CardStatus | Aruba Controller Card Status | 3.0.0 | Provides Aruba controller card type and the status. Possible card types are 1- LC1,2- LC2,3- SC1,4- SC2,5- SW2400,6- SW800,7- SW200,8- M3MK1,9- SW3200,10- SW3400,11- SW3600. Possible card status values are 1- Active,2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.16.1.2,1.3.6.1.4.1.14823.2.2.1.2.1.16.1.12]. | ||
| aruba_wlan_controller_instanton_SwitchStatus | Aruba Controller Switch Status | 3.0.0 | Provides Aruba controller switch status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.6, 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.2, 1.3.6.1.4.1.14823.2.2.1.2.1.19.1.5]. | ||
| aruba_wlan_controller_instanton_fanStatus | Aruba Controller Fan Status | 3.0.0 | Provides Aruba controller fan status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.17.1.2]. | ||
| aruba_wlan_controller_instanton_PowerSupplyStatus | Aruba Controller Power Supply Status | 3.0.0 | Provides Aruba controller powersupply status. Possible status values are 1- Active, 2- Inactive. [OID: 1.3.6.1.4.1.14823.2.2.1.2.1.18.1.2]. |
Default Monitoring Configurations
wlan-controller have default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. User can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommend to do this activity before installing the app to avoid noise alerts and data.
Default Global Device Management Policies available OpsRamp will have a Global Device Management Policy for the Native Type of Wireless LAN Controller. We can find those Device Management Policies at Setup -> Resources -> Device Management Policies -> Search with suggested names in global scope. Each Device Management Policy follows below naming convention:
{appName nativeType - version}Example: wlan-controller Wireless LAN Controller - 1 (i.e, appName = wlan-controller, nativeType = Wireless LAN Controller , version = 1)
Default Global Templates available OpsRamp will have a Global template for the Native Type of Wireless LAN Controller. We can find those templates at Setup -> Monitoring -> Templates -> Search with suggested names in global scope. Each template follows below naming convention:
{appName nativeType 'Template' - version}Example: wlan-controller Wireless LAN Controller Template - 1 (i.e, appName = wlan-controller, nativeType = Wireless LAN Controller, version = 1)
Default Global Monitors available OpsRamp will have a Global Monitors for the Native Type which has monitoring support. We can find those monitors at Setup -> Monitoring -> Monitors -> Search with suggested names in global scope. Each Monitors follows below naming convention:
{monitorKey appName nativeType - version}Example: Wireless LAN Controller Monitor wlan-controller Wireless LAN Controller 1 (i.e, monitorKey =Wireless LAN Controller Monitor, appName = wlan-controller, nativeType = Wireless LAN Controller , version = 1)